hi this is my first post
the result isn't correct i always obtain 0.00 also if, for example, i write 8 and 2 as scanned number. why?Code:#include <stdio.h> #include <stdlib.h> int main() { int a,b; printf("Insert 2 numbers:\n"); scanf("%d%d",&a,&b); printf("Result is: %f \n",a/b); system("pause"); return 0; }
Try printing a and b to see that you're actually getting numbers. Also, integer division will always yield integer results.
Quzah.
Hope is the first step on the road to disappointment.
cast a/b to floats with something like
(float) a / (float) b;
That provides a float result.
As it is, you're probably sending an integer when printf is expecting a float, which might easily produce nonsense.
Change "might" into "will" - floating point numbers are quite different from integers in their internal components. So there is no chance that a floating point number will make much sense as an integer or the other way around. It'll look as nice as monkeys typing on a calculator.Originally Posted by JVene
It would actually make sense to use a cast to double rather than float, since printf doesn't ever take a float argument - all floating point values will convert to double before printf gets to see the value. And you only need to cast one side of the operator, so:
should give the right result.Code:printf("%f\n", (double)a / b);
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Ah, true - doubles....yish, I should probably stay in the C++ forum, my C is rusty.
NITPICK: 0 can be represented the same way a integers and floating point. (And usually is, though sometimes -0 is used, which is equal the minimum integer value instead.)
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
